fix: Deploy TrinoCatalogs before TrinoClusters#383
Merged
NickLarsenNZ merged 6 commits intomainfrom Mar 13, 2026
Merged
Conversation
…efore TrinoCluster
This was referenced Mar 12, 2026
sbernauer
approved these changes
Mar 13, 2026
sbernauer
moved this from Development: Waiting for Review
to Development: In Review
in Stackable Engineering
NickLarsenNZ
moved this from Development: In Review
to Development: Done
in Stackable Engineering
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In Kubernetes 1.35, TrinoCatalogs need to be deployed before TrinoClusters.
See stackabletech/trino-operator#854 for further detail.
Note
A sibling PR for relesae-25.11 is here: #382
Tested for the
spark-trino-superset-s3stack.